Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f3801975d5dd054240223915650b4e75e5b204e9e4395aa3c1d743e697f5956

Tx prefix hash: a6cccce9cccf048138e16ac9a7e524b3e596c13f00124097095c577841566ae8
Tx public key: 8290397f9c5fd4c305950e5f7d98894dd2aa40ac198c1a8800c77f491839a821
Timestamp: 1631375202 Timestamp [UCT]: 2021-09-11 15:46:42 Age [y:d:h:m:s]: 03:107:05:43:24
Block: 331733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 852114 RingCT/type: yes/0
Extra: 018290397f9c5fd4c305950e5f7d98894dd2aa40ac198c1a8800c77f491839a821021100000037fdc024ec000000000000000000

1 output(s) for total of 48.848978794000 dcy

stealth address amount amount idx
00: 0813c0596fa58662f50639a188707625170e76f0ea7e160af67fad6b4cd76aae 48.848978794000 685380 of 0

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": 331743, "vin": [ { "gen": { "height": 331733 } } ], "vout": [ { "amount": 48848978794, "target": { "key": "0813c0596fa58662f50639a188707625170e76f0ea7e160af67fad6b4cd76aae" } } ], "extra": [ 1, 130, 144, 57, 127, 156, 95, 212, 195, 5, 149, 14, 95, 125, 152, 137, 77, 210, 170, 64, 172, 25, 140, 26, 136, 0, 199, 127, 73, 24, 57, 168, 33, 2, 17, 0, 0, 0, 55, 253, 192, 36, 236, 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