Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a3b71b3a841cd8c8548ca1833a3796a28e89d83ad0764f6036e782b574b1420

Tx prefix hash: d4f312d3fff3be2618e4c44a376b25b933c337c869d0bafbe7e6a0e1ace65789
Tx public key: 5ae81366f5c8e4f110b290336d18f4129ccde0bc1bf0d511641f8a3372e0308f
Timestamp: 1579273874 Timestamp [UCT]: 2020-01-17 15:11:14 Age [y:d:h:m:s]: 05:020:14:44:14
Block: 47787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164652 RingCT/type: yes/0
Extra: 015ae81366f5c8e4f110b290336d18f4129ccde0bc1bf0d511641f8a3372e0308f02110000000849b77a3d000000000000000000

1 output(s) for total of 426.248307836000 dcy

stealth address amount amount idx
00: 8bc5686d0fd9bbddf155c8393ce96d2cdc8fee56c5c83f742f42400261c4ea9d 426.248307836000 88220 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": 47797, "vin": [ { "gen": { "height": 47787 } } ], "vout": [ { "amount": 426248307836, "target": { "key": "8bc5686d0fd9bbddf155c8393ce96d2cdc8fee56c5c83f742f42400261c4ea9d" } } ], "extra": [ 1, 90, 232, 19, 102, 245, 200, 228, 241, 16, 178, 144, 51, 109, 24, 244, 18, 156, 205, 224, 188, 27, 240, 213, 17, 100, 31, 138, 51, 114, 224, 48, 143, 2, 17, 0, 0, 0, 8, 73, 183, 122, 61, 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