Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e77eab4bdc6cb8291ba12ad4f696a5007b642bb9d4d8fe2d3d12bacd11bf529

Tx prefix hash: eb071d9a8bb69c1358f406636f9af91c606e358df358c05dec6f5a42069f74f2
Tx public key: 31f8c260ca87b6f807a015cdfc9e16cfd6881c43e6040d016f52a0ed7e46bb98
Timestamp: 1728463567 Timestamp [UCT]: 2024-10-09 08:46:07 Age [y:d:h:m:s]: 00:178:07:45:53
Block: 1127713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127248 RingCT/type: yes/0
Extra: 0131f8c260ca87b6f807a015cdfc9e16cfd6881c43e6040d016f52a0ed7e46bb9802110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5e1566891717f43a1cf6a136aaa618de8d1bb81aea1494e277ee188fa7ddbcc 0.600000000000 1610524 of 15

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": 1127723, "vin": [ { "gen": { "height": 1127713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5e1566891717f43a1cf6a136aaa618de8d1bb81aea1494e277ee188fa7ddbcc" } } ], "extra": [ 1, 49, 248, 194, 96, 202, 135, 182, 248, 7, 160, 21, 205, 252, 158, 22, 207, 214, 136, 28, 67, 230, 4, 13, 1, 111, 82, 160, 237, 126, 70, 187, 152, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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