Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d73734d277ac1aee7140afbb08898e894d98778e40a97ce3c4c9816f0ec9e33

Tx prefix hash: a5e6e2eb03cffc352834364291a5fd91a8dc9d1b997efebc73860b7a3942bf7d
Tx public key: 1ad63eae584fe7699585fc66befd35e532992aa2e8c4de4bf1db131ce2753e14
Timestamp: 1717420369 Timestamp [UCT]: 2024-06-03 13:12:49 Age [y:d:h:m:s]: 00:285:10:05:31
Block: 1036181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203992 RingCT/type: yes/0
Extra: 011ad63eae584fe7699585fc66befd35e532992aa2e8c4de4bf1db131ce2753e140211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a4318040a4da2e63e7ea2f3830736eccfcce931eac59c8be9b2e161f7141c52 0.600000000000 1504706 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": 1036191, "vin": [ { "gen": { "height": 1036181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a4318040a4da2e63e7ea2f3830736eccfcce931eac59c8be9b2e161f7141c52" } } ], "extra": [ 1, 26, 214, 62, 174, 88, 79, 231, 105, 149, 133, 252, 102, 190, 253, 53, 229, 50, 153, 42, 162, 232, 196, 222, 75, 241, 219, 19, 28, 226, 117, 62, 20, 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