Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcd1ce008ef3f9ae4347500267662e1f0054b38bc6f94c5224a304febaa9620a

Tx prefix hash: 67fc85a2c071e95d0609c7ac1636a43ddf67b8680d051512e0ae5b10ebed501d
Tx public key: baf8a4e5e9beaa11bdaff0ce6f40faadf4a2ce2f135d0d9b0e452bd7be39cf05
Timestamp: 1718819025 Timestamp [UCT]: 2024-06-19 17:43:45 Age [y:d:h:m:s]: 00:345:14:27:54
Block: 1047759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247017 RingCT/type: yes/0
Extra: 01baf8a4e5e9beaa11bdaff0ce6f40faadf4a2ce2f135d0d9b0e452bd7be39cf0502110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6e3f39c24e2727c0ffe8af408f9e46de3ec230c545475adda79298cff78bb45 0.600000000000 1517666 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": 1047769, "vin": [ { "gen": { "height": 1047759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6e3f39c24e2727c0ffe8af408f9e46de3ec230c545475adda79298cff78bb45" } } ], "extra": [ 1, 186, 248, 164, 229, 233, 190, 170, 17, 189, 175, 240, 206, 111, 64, 250, 173, 244, 162, 206, 47, 19, 93, 13, 155, 14, 69, 43, 215, 190, 57, 207, 5, 2, 17, 0, 0, 0, 9, 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