Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87758915bc74009ea8aa14b56065cab8e71498c9c4574d11c3c848969f73d1e2

Tx prefix hash: 6e5c84c60ed7bada60873cfcaf9f6ae69e9ac1aa26daeae5b048aed17a0ce2d1
Tx public key: d4a5b58a43876b27dec2f877f93dc6b4331a2940baaa513eaa936915a3f2f1d2
Timestamp: 1577265048 Timestamp [UCT]: 2019-12-25 09:10:48 Age [y:d:h:m:s]: 05:006:08:10:22
Block: 31283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154587 RingCT/type: yes/0
Extra: 01d4a5b58a43876b27dec2f877f93dc6b4331a2940baaa513eaa936915a3f2f1d20211000000f1ac34bf9e000000000000000000

1 output(s) for total of 483.458897444000 dcy

stealth address amount amount idx
00: 72c374e24487d351101ec6ed7219da80953c899a81be6d5b080cfc4f6eec1623 483.458897444000 51721 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": 31293, "vin": [ { "gen": { "height": 31283 } } ], "vout": [ { "amount": 483458897444, "target": { "key": "72c374e24487d351101ec6ed7219da80953c899a81be6d5b080cfc4f6eec1623" } } ], "extra": [ 1, 212, 165, 181, 138, 67, 135, 107, 39, 222, 194, 248, 119, 249, 61, 198, 180, 51, 26, 41, 64, 186, 170, 81, 62, 170, 147, 105, 21, 163, 242, 241, 210, 2, 17, 0, 0, 0, 241, 172, 52, 191, 158, 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