Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf86511d4d4ee54d4e85dd8e8509438b62886134cecf19a5c15e0f50de3573b5

Tx prefix hash: 4ab01549cfb21be7654f3593913eca1c9ac7a747ba7f6d9be022a16e9e4279ae
Tx public key: fdc745fce7f37308d41fa57a388670802df1c8607c13a16b2356108b9c2732ba
Timestamp: 1716147545 Timestamp [UCT]: 2024-05-19 19:39:05 Age [y:d:h:m:s]: 00:283:14:23:11
Block: 1025614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202680 RingCT/type: yes/0
Extra: 01fdc745fce7f37308d41fa57a388670802df1c8607c13a16b2356108b9c2732ba02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dc437a4853775c41aebecb2ecf1f0b46f933783778ac5d9a79ea2af5963ba5e 0.600000000000 1492247 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": 1025624, "vin": [ { "gen": { "height": 1025614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dc437a4853775c41aebecb2ecf1f0b46f933783778ac5d9a79ea2af5963ba5e" } } ], "extra": [ 1, 253, 199, 69, 252, 231, 243, 115, 8, 212, 31, 165, 122, 56, 134, 112, 128, 45, 241, 200, 96, 124, 19, 161, 107, 35, 86, 16, 139, 156, 39, 50, 186, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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