Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0d77c55e165b562ce8164160ac9259fef9a1a4480781af87f113f349cd5fac2

Tx prefix hash: ae764cf03701f3cca92f9e19a93b5157420f07f86f72034c2d272978b98f8cb0
Tx public key: 6be9e9c6d21e78d696d2334bd2e740697e1c01b74b2dbf845fc724917c334708
Timestamp: 1636944835 Timestamp [UCT]: 2021-11-15 02:53:55 Age [y:d:h:m:s]: 03:350:23:16:30
Block: 374539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1027084 RingCT/type: yes/0
Extra: 016be9e9c6d21e78d696d2334bd2e740697e1c01b74b2dbf845fc724917c33470802110000000ae9564d6f000000000000000000

1 output(s) for total of 35.237470094000 dcy

stealth address amount amount idx
00: 040e9aa407a32c7bd62e014e471c446fabe26ae9a5c339f0c38cb0365cac8454 35.237470094000 758081 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": 374549, "vin": [ { "gen": { "height": 374539 } } ], "vout": [ { "amount": 35237470094, "target": { "key": "040e9aa407a32c7bd62e014e471c446fabe26ae9a5c339f0c38cb0365cac8454" } } ], "extra": [ 1, 107, 233, 233, 198, 210, 30, 120, 214, 150, 210, 51, 75, 210, 231, 64, 105, 126, 28, 1, 183, 75, 45, 191, 132, 95, 199, 36, 145, 124, 51, 71, 8, 2, 17, 0, 0, 0, 10, 233, 86, 77, 111, 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