Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 970d4676f02297bdac7c6f2c8c899bf4fcbf34b2afffa321c1d77f49608f134d

Tx prefix hash: 3290d736b5a17c90fbe463bb0445074f0f031e7a75fdbe21db3b4a6bb0938404
Tx public key: c416aa72e462b40c073fe538d78c9a08ba7db588b76af8c14f2edf193d93e4c7
Timestamp: 1746102786 Timestamp [UCT]: 2025-05-01 12:33:06 Age [y:d:h:m:s]: 00:204:11:30:38
Block: 1273432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143864 RingCT/type: yes/0
Extra: 01c416aa72e462b40c073fe538d78c9a08ba7db588b76af8c14f2edf193d93e4c70211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b85f163666c863d7e0841614eb10dd0f286d8f8a20a3a71cd926f161c09427da 0.600000000000 1760713 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": 1273442, "vin": [ { "gen": { "height": 1273432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b85f163666c863d7e0841614eb10dd0f286d8f8a20a3a71cd926f161c09427da" } } ], "extra": [ 1, 196, 22, 170, 114, 228, 98, 180, 12, 7, 63, 229, 56, 215, 140, 154, 8, 186, 125, 181, 136, 183, 106, 248, 193, 79, 46, 223, 25, 61, 147, 228, 199, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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