Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f53d5f6151dc109fdb718d94130427727acb6d6936ee0a10f8d0d7563423b20b

Tx prefix hash: edddfa05aae22fe7e47757924b0b61699909f99a9cc6466b200ffe5d8b0bd320
Tx public key: 739fdcfe5846bbb0577e48e4bfcd522bc83a62547f8c477ae0f0160515f81d0d
Timestamp: 1725630018 Timestamp [UCT]: 2024-09-06 13:40:18 Age [y:d:h:m:s]: 01:063:11:22:11
Block: 1104232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303787 RingCT/type: yes/0
Extra: 01739fdcfe5846bbb0577e48e4bfcd522bc83a62547f8c477ae0f0160515f81d0d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3318ed10af4fc03fc76226529a0e13a5fb4a3a596a33869f0a72832dfd3dae0a 0.600000000000 1581311 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": 1104242, "vin": [ { "gen": { "height": 1104232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3318ed10af4fc03fc76226529a0e13a5fb4a3a596a33869f0a72832dfd3dae0a" } } ], "extra": [ 1, 115, 159, 220, 254, 88, 70, 187, 176, 87, 126, 72, 228, 191, 205, 82, 43, 200, 58, 98, 84, 127, 140, 71, 122, 224, 240, 22, 5, 21, 248, 29, 13, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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