Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9396a72222bb9b195e15ea4e6fa087dcc9bdc73a44f5cf1f786d61458e8e94a

Tx prefix hash: 49fb12cd4f386f74e739a597b985fb8e5ed9f6ee843d5438409d90dcc333d2c3
Tx public key: 0a9025fd10583d3ab36e02a2cd7e92e5960858979648d0992990f0f05ec7f42f
Timestamp: 1682811946 Timestamp [UCT]: 2023-04-29 23:45:46 Age [y:d:h:m:s]: 01:347:03:24:06
Block: 749500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509358 RingCT/type: yes/0
Extra: 010a9025fd10583d3ab36e02a2cd7e92e5960858979648d0992990f0f05ec7f42f0211000000027e406890000000000000000000

1 output(s) for total of 2.016487674000 dcy

stealth address amount amount idx
00: 4926ad53be2ed21b849a9ca76041ff2da976efb932b2fd2e3678af733b0e5a6e 2.016487674000 1197475 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": 749510, "vin": [ { "gen": { "height": 749500 } } ], "vout": [ { "amount": 2016487674, "target": { "key": "4926ad53be2ed21b849a9ca76041ff2da976efb932b2fd2e3678af733b0e5a6e" } } ], "extra": [ 1, 10, 144, 37, 253, 16, 88, 61, 58, 179, 110, 2, 162, 205, 126, 146, 229, 150, 8, 88, 151, 150, 72, 208, 153, 41, 144, 240, 240, 94, 199, 244, 47, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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