Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a7c84d275ff9f18226a988415e118d99f19cf6343e3bc712d7bf2ae036e8534

Tx prefix hash: cd15be9e97f9721e2b6dc9818dece8ac35987f3919193d78a0f8bbaa5cade82e
Tx public key: c4a14c0e15fc80877a45c4456ed7da93e746c3013a68c4642056a967f8031933
Timestamp: 1574700604 Timestamp [UCT]: 2019-11-25 16:50:04 Age [y:d:h:m:s]: 05:037:03:06:08
Block: 17279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169379 RingCT/type: yes/0
Extra: 01c4a14c0e15fc80877a45c4456ed7da93e746c3013a68c4642056a967f80319330211000000080b4dd45a000000000000000000

1 output(s) for total of 537.958013191000 dcy

stealth address amount amount idx
00: f17e82fe8dce854717f2879549b6fc102912a2d19a151d67adc5a226a9bf77b6 537.958013191000 24917 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": 17289, "vin": [ { "gen": { "height": 17279 } } ], "vout": [ { "amount": 537958013191, "target": { "key": "f17e82fe8dce854717f2879549b6fc102912a2d19a151d67adc5a226a9bf77b6" } } ], "extra": [ 1, 196, 161, 76, 14, 21, 252, 128, 135, 122, 69, 196, 69, 110, 215, 218, 147, 231, 70, 195, 1, 58, 104, 196, 100, 32, 86, 169, 103, 248, 3, 25, 51, 2, 17, 0, 0, 0, 8, 11, 77, 212, 90, 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