Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0118a4506fdd52962c32042aecc235f2f53b7eafba88f4a3c012296beeada9c9

Tx prefix hash: 7ed93a0351b1fc623b762e2e51b7ece001d6b4e23ebeea65a0759faa5d2da5e8
Tx public key: 03744934fd1b60ae5e8d9eb03ccdbd14e7b85df94fab768edbc0b233bd5b2916
Timestamp: 1758172604 Timestamp [UCT]: 2025-09-18 05:16:44 Age [y:d:h:m:s]: 00:109:19:35:48
Block: 1370910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78652 RingCT/type: yes/0
Extra: 0103744934fd1b60ae5e8d9eb03ccdbd14e7b85df94fab768edbc0b233bd5b2916021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5693bc9941f8c4f55eea259459bb6ab80b2de8468009dab9b89eb46b939dd7cc 0.600000000000 1858987 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": 1370920, "vin": [ { "gen": { "height": 1370910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5693bc9941f8c4f55eea259459bb6ab80b2de8468009dab9b89eb46b939dd7cc" } } ], "extra": [ 1, 3, 116, 73, 52, 253, 27, 96, 174, 94, 141, 158, 176, 60, 205, 189, 20, 231, 184, 93, 249, 79, 171, 118, 142, 219, 192, 178, 51, 189, 91, 41, 22, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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