Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cb480f8a4a9ad606283081f0b49d486e819f741cd8d5382a315949ce044f6e9

Tx prefix hash: c0eb0cbb3faecfb6fee2087c766c460e3315a8335829567df45e49a9e7dfdbee
Tx public key: 0fff4e04eb861b1ba9420d9902af887a5ca37e9b29f5b32376188a9cfa7762cf
Timestamp: 1728246230 Timestamp [UCT]: 2024-10-06 20:23:50 Age [y:d:h:m:s]: 00:185:10:23:19
Block: 1125915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132335 RingCT/type: yes/0
Extra: 010fff4e04eb861b1ba9420d9902af887a5ca37e9b29f5b32376188a9cfa7762cf02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7849272be309b6272f3aad8a6f11c9625174b79de1b7ae80a066734508551041 0.600000000000 1608688 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": 1125925, "vin": [ { "gen": { "height": 1125915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7849272be309b6272f3aad8a6f11c9625174b79de1b7ae80a066734508551041" } } ], "extra": [ 1, 15, 255, 78, 4, 235, 134, 27, 27, 169, 66, 13, 153, 2, 175, 136, 122, 92, 163, 126, 155, 41, 245, 179, 35, 118, 24, 138, 156, 250, 119, 98, 207, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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