Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaec6756bedaa3e2ed07830a2c820b7a8a2bc543be200221d197a524051b28bf

Tx prefix hash: 9ec520cba564572e9d79f26fbfdaf3d9263a8f7f287cb219f815fd51824a3081
Tx public key: ea9bbde824ea9f973f4eeda1d2ad74469548ec89cc33b103e3ee0f5c58bd4d08
Timestamp: 1724039311 Timestamp [UCT]: 2024-08-19 03:48:31 Age [y:d:h:m:s]: 00:224:06:22:18
Block: 1091052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160138 RingCT/type: yes/0
Extra: 01ea9bbde824ea9f973f4eeda1d2ad74469548ec89cc33b103e3ee0f5c58bd4d08021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32aac2890fa949286dbf95885e5aa87407b0afcb3f9ef01247d8d27d7fb35a19 0.600000000000 1565677 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": 1091062, "vin": [ { "gen": { "height": 1091052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32aac2890fa949286dbf95885e5aa87407b0afcb3f9ef01247d8d27d7fb35a19" } } ], "extra": [ 1, 234, 155, 189, 232, 36, 234, 159, 151, 63, 78, 237, 161, 210, 173, 116, 70, 149, 72, 236, 137, 204, 51, 177, 3, 227, 238, 15, 92, 88, 189, 77, 8, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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