Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53c1ec32899b963b3d2f94c8ff019ee0d4a1f4d5982a6285b0d62af9ab27afd8

Tx prefix hash: 8e743c15fd207972c606fbeaf307bc692c01bc455d6d368aaa7ffbd8b277ea21
Tx public key: 0eab9d6d23232caedd11ac0c2d88cf65d54a006233e7d3792e64c11fa579a263
Timestamp: 1701606760 Timestamp [UCT]: 2023-12-03 12:32:40 Age [y:d:h:m:s]: 01:084:23:49:07
Block: 905061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321864 RingCT/type: yes/0
Extra: 010eab9d6d23232caedd11ac0c2d88cf65d54a006233e7d3792e64c11fa579a26302110000000633af99f4000000000000000000

1 output(s) for total of 0.615399550000 dcy

stealth address amount amount idx
00: 4217a583d74f1535109109fcb538d9ad7cb222de81fb14d4f0636c07000662cb 0.615399550000 1361926 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": 905071, "vin": [ { "gen": { "height": 905061 } } ], "vout": [ { "amount": 615399550, "target": { "key": "4217a583d74f1535109109fcb538d9ad7cb222de81fb14d4f0636c07000662cb" } } ], "extra": [ 1, 14, 171, 157, 109, 35, 35, 44, 174, 221, 17, 172, 12, 45, 136, 207, 101, 213, 74, 0, 98, 51, 231, 211, 121, 46, 100, 193, 31, 165, 121, 162, 99, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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