Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5162d63d6c908fb2f9dc68a666cdd997dada7c648b0223bd9d9971514a457c3

Tx prefix hash: abd2d103b2f5bdf33e98a5a712b757159dad29f28421182ed968c48624a32131
Tx public key: 1d5dd6d85a964ae9617a0f4f0815b6c6bf4417c5c54fcca124b1ae03d91442a8
Timestamp: 1731537084 Timestamp [UCT]: 2024-11-13 22:31:24 Age [y:d:h:m:s]: 00:010:12:26:30
Block: 1153120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7518 RingCT/type: yes/0
Extra: 011d5dd6d85a964ae9617a0f4f0815b6c6bf4417c5c54fcca124b1ae03d91442a8021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9ca048f1a7b6d367126db5ebdfb6b5b66fffdd4ae6798584e906b8dd545ffc 0.600000000000 1638727 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": 1153130, "vin": [ { "gen": { "height": 1153120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9ca048f1a7b6d367126db5ebdfb6b5b66fffdd4ae6798584e906b8dd545ffc" } } ], "extra": [ 1, 29, 93, 214, 216, 90, 150, 74, 233, 97, 122, 15, 79, 8, 21, 182, 198, 191, 68, 23, 197, 197, 79, 204, 161, 36, 177, 174, 3, 217, 20, 66, 168, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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