Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15544836e7de68bfb6ee4ba01b939fd35f0482005dbd53707537f13f7c1c1f52

Tx prefix hash: 5236210c48fe3901a0b01f788fb601a6b1facfb0b003c3c8a2f1445e9a56721e
Tx public key: 1d321783aada1d64e017301aea5152100b2ce1a1dc8c2439e318efd8257b9e84
Timestamp: 1732470078 Timestamp [UCT]: 2024-11-24 17:41:18 Age [y:d:h:m:s]: 00:127:01:50:41
Block: 1160839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90635 RingCT/type: yes/0
Extra: 011d321783aada1d64e017301aea5152100b2ce1a1dc8c2439e318efd8257b9e84021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ee808afb45c401852ead7016efe12c749ba0f6598cb2895b30e04c47dbbcfd8 0.600000000000 1646490 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": 1160849, "vin": [ { "gen": { "height": 1160839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ee808afb45c401852ead7016efe12c749ba0f6598cb2895b30e04c47dbbcfd8" } } ], "extra": [ 1, 29, 50, 23, 131, 170, 218, 29, 100, 224, 23, 48, 26, 234, 81, 82, 16, 11, 44, 225, 161, 220, 140, 36, 57, 227, 24, 239, 216, 37, 123, 158, 132, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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