Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7f4d308fae4dd53bdd7f21d17d1b428c728ce05da30b6948699dd1774b53282f

Tx prefix hash: b4e7a681211d77ba53869733298473c6e58fd70bf6814f0a3a5bc65d82590e96
Tx public key: 0e918629572d6b39a6c3bcaf521cfdca10e207d3fb31305e7cdd8c89b1229652
Timestamp: 1706676459 Timestamp [UCT]: 2024-01-31 04:47:39 Age [y:d:h:m:s]: 01:030:03:20:17
Block: 947073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282598 RingCT/type: yes/0
Extra: 010e918629572d6b39a6c3bcaf521cfdca10e207d3fb31305e7cdd8c89b12296520211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c4c5331896ec3585d508ba814fdbecfa53303a9f681c4237f92d2771ad2c590 0.600000000000 1405421 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 947083, "vin": [ { "gen": { "height": 947073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c4c5331896ec3585d508ba814fdbecfa53303a9f681c4237f92d2771ad2c590" } } ], "extra": [ 1, 14, 145, 134, 41, 87, 45, 107, 57, 166, 195, 188, 175, 82, 28, 253, 202, 16, 226, 7, 211, 251, 49, 48, 94, 124, 221, 140, 137, 177, 34, 150, 82, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8