Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc62f327c8a91b8bbfa192cf0119f68fe2f6283d3613354284821c0123ef9a0b

Tx prefix hash: 0ff3789afb072a35f21b993dcd9542bf66aa29aff1780254a7acd556b59ead40
Tx public key: efcbe24d32e5f34144d9c9668159e76e67c169b2835675683e53a9f317ef54c1
Timestamp: 1718248174 Timestamp [UCT]: 2024-06-13 03:09:34 Age [y:d:h:m:s]: 00:338:04:43:48
Block: 1043034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241714 RingCT/type: yes/0
Extra: 01efcbe24d32e5f34144d9c9668159e76e67c169b2835675683e53a9f317ef54c10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 215e4bd64b3fdaf07ce0c79cbe15d96feb4ab4bbf63b915fd6d1e1bb7b997f1d 0.600000000000 1512089 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": 1043044, "vin": [ { "gen": { "height": 1043034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "215e4bd64b3fdaf07ce0c79cbe15d96feb4ab4bbf63b915fd6d1e1bb7b997f1d" } } ], "extra": [ 1, 239, 203, 226, 77, 50, 229, 243, 65, 68, 217, 201, 102, 129, 89, 231, 110, 103, 193, 105, 178, 131, 86, 117, 104, 62, 83, 169, 243, 23, 239, 84, 193, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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