Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 495a8da44506e631e7478dc1813378b005347c45230da257f39a91e9194bb5a4

Tx prefix hash: 89466f8a2e1e45a43a2459915947288f88c8a231bacb3944b4c8540afd9883fc
Tx public key: dee58ec506b58978f5f0950b19440e37a8c3601f7a76bb5c011a5abfd54e2785
Timestamp: 1706232263 Timestamp [UCT]: 2024-01-26 01:24:23 Age [y:d:h:m:s]: 01:081:20:42:40
Block: 943381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319615 RingCT/type: yes/0
Extra: 01dee58ec506b58978f5f0950b19440e37a8c3601f7a76bb5c011a5abfd54e278502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5c4fbc58305434337df3e713f82c2987fc73a05a6877534344775a3ea34c0a 0.600000000000 1401587 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": 943391, "vin": [ { "gen": { "height": 943381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5c4fbc58305434337df3e713f82c2987fc73a05a6877534344775a3ea34c0a" } } ], "extra": [ 1, 222, 229, 142, 197, 6, 181, 137, 120, 245, 240, 149, 11, 25, 68, 14, 55, 168, 195, 96, 31, 122, 118, 187, 92, 1, 26, 90, 191, 213, 78, 39, 133, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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