Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3689f2900104338b365da708139dc28773fdfb3f74a76f26643ff9541bbdce5a

Tx prefix hash: 48fdd1cb4f15a6b8fc49c75f203665ae00c2d794752d8ed7553d6364dbc0e62e
Tx public key: 07d5eca579e781218fbb2f9f032f7c8c2c64db58e634a9461f18d4f38e038bb1
Timestamp: 1764977540 Timestamp [UCT]: 2025-12-05 23:32:20 Age [y:d:h:m:s]: 00:017:08:20:09
Block: 1427304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12424 RingCT/type: yes/0
Extra: 0107d5eca579e781218fbb2f9f032f7c8c2c64db58e634a9461f18d4f38e038bb1021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98265bb7804f5ceeb955e6cbf3a48197eb0482598f10701521a6bdc9a5d793f6 0.600000000000 1916005 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": 1427314, "vin": [ { "gen": { "height": 1427304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98265bb7804f5ceeb955e6cbf3a48197eb0482598f10701521a6bdc9a5d793f6" } } ], "extra": [ 1, 7, 213, 236, 165, 121, 231, 129, 33, 143, 187, 47, 159, 3, 47, 124, 140, 44, 100, 219, 88, 230, 52, 169, 70, 31, 24, 212, 243, 142, 3, 139, 177, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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