Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0d48f7067f43808a662f936a5a92317bac38edb89bf6379bcc46af9df572b0

Tx prefix hash: f36d0fcfb8b75b394fb35463bc342a84cba8f96483d316d7d704dcdb6a5f9bb7
Tx public key: 5b3152588b3e638f8f1fb19cfccbb629e57a90deecb72697ceaea105b9a3aef2
Timestamp: 1732903611 Timestamp [UCT]: 2024-11-29 18:06:51 Age [y:d:h:m:s]: 00:109:19:56:31
Block: 1164437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78314 RingCT/type: yes/0
Extra: 015b3152588b3e638f8f1fb19cfccbb629e57a90deecb72697ceaea105b9a3aef2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6cd7175de4bda69b15690fb5d072b04144b6fd18f1c1de99cad6938316512b7 0.600000000000 1650110 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": 1164447, "vin": [ { "gen": { "height": 1164437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6cd7175de4bda69b15690fb5d072b04144b6fd18f1c1de99cad6938316512b7" } } ], "extra": [ 1, 91, 49, 82, 88, 139, 62, 99, 143, 143, 31, 177, 156, 252, 203, 182, 41, 229, 122, 144, 222, 236, 183, 38, 151, 206, 174, 161, 5, 185, 163, 174, 242, 2, 17, 0, 0, 0, 2, 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