Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5b371b126a6f7592451a54e10e717befc5d7d36139a4fbde452e3c0d6f5e41

Tx prefix hash: ac6968a1670c17bdea6953211d2ef8ecb9481caac0e869f5c8c0885cf256773e
Tx public key: e1d911da6026990875f9b6375307d75a343f9a568340f70541583050f74399e2
Timestamp: 1735464105 Timestamp [UCT]: 2024-12-29 09:21:45 Age [y:d:h:m:s]: 00:174:19:02:18
Block: 1185623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124593 RingCT/type: yes/0
Extra: 01e1d911da6026990875f9b6375307d75a343f9a568340f70541583050f74399e20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 025e1395fb54303122a14c834128178c3f2e0f34d8c489552928e8f784e3d5a1 0.600000000000 1672098 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": 1185633, "vin": [ { "gen": { "height": 1185623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "025e1395fb54303122a14c834128178c3f2e0f34d8c489552928e8f784e3d5a1" } } ], "extra": [ 1, 225, 217, 17, 218, 96, 38, 153, 8, 117, 249, 182, 55, 83, 7, 215, 90, 52, 63, 154, 86, 131, 64, 247, 5, 65, 88, 48, 80, 247, 67, 153, 226, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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