Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c51ba0a1c868e3038c4f691e8dad190b9b6e6987e7a1149cc60328e0f59cd03e

Tx prefix hash: 788dee89b95b10af4f259151349c2d118ddf3fcf55ab3538c177b0676a5640ab
Tx public key: d5938a01d0928a1923c0fbe67fae19750dc37ebda76ab8a5f3477fb5d4c78aad
Timestamp: 1741265617 Timestamp [UCT]: 2025-03-06 12:53:37 Age [y:d:h:m:s]: 00:300:19:30:20
Block: 1233402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212793 RingCT/type: yes/0
Extra: 01d5938a01d0928a1923c0fbe67fae19750dc37ebda76ab8a5f3477fb5d4c78aad021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea2ac64c1c6f7abcca349270eb36c4a1b1a13bc507052f3be48fc0376548b0d3 0.600000000000 1720323 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": 1233412, "vin": [ { "gen": { "height": 1233402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea2ac64c1c6f7abcca349270eb36c4a1b1a13bc507052f3be48fc0376548b0d3" } } ], "extra": [ 1, 213, 147, 138, 1, 208, 146, 138, 25, 35, 192, 251, 230, 127, 174, 25, 117, 13, 195, 126, 189, 167, 106, 184, 165, 243, 71, 127, 181, 212, 199, 138, 173, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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