Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e820bed5ecf6da4706743ec997a4cd7b2ea5d5b0df81f054954619efc0ee900e

Tx prefix hash: 6e778656d30ebc6fdb68fe558f66b06c531e912ceedc0a7f9f41e4aaf5ece3f9
Tx public key: 54904238d136f9bbf8952f0c3de7485dfafaf816722bd357126ed83c12fde240
Timestamp: 1669244547 Timestamp [UCT]: 2022-11-23 23:02:27 Age [y:d:h:m:s]: 02:187:09:37:04
Block: 637670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 655702 RingCT/type: yes/0
Extra: 0154904238d136f9bbf8952f0c3de7485dfafaf816722bd357126ed83c12fde24002110000000183600029000000000000000000

1 output(s) for total of 4.732979084000 dcy

stealth address amount amount idx
00: adfded43f1408917a284791c3c8c559bf4e4d0df475dc7d68e4f37e8f9fcb6b9 4.732979084000 1077255 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": 637680, "vin": [ { "gen": { "height": 637670 } } ], "vout": [ { "amount": 4732979084, "target": { "key": "adfded43f1408917a284791c3c8c559bf4e4d0df475dc7d68e4f37e8f9fcb6b9" } } ], "extra": [ 1, 84, 144, 66, 56, 209, 54, 249, 187, 248, 149, 47, 12, 61, 231, 72, 93, 250, 250, 248, 22, 114, 43, 211, 87, 18, 110, 216, 60, 18, 253, 226, 64, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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