Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05bf6efae48bbadaae9fe2193acd8fb91b3049395d62deda259653fdce287c6a

Tx prefix hash: a5429dc1991916c0f2f5d6a85434f0e34d0e3bd669feddca5576f5e7a5ce89e8
Tx public key: 637c26b29c72e1c8ef9f27b25cc34bbe2f90404ffb477e899bbde9afe0c53c64
Timestamp: 1717537453 Timestamp [UCT]: 2024-06-04 21:44:13 Age [y:d:h:m:s]: 00:142:14:33:17
Block: 1037151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102098 RingCT/type: yes/0
Extra: 01637c26b29c72e1c8ef9f27b25cc34bbe2f90404ffb477e899bbde9afe0c53c6402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1e3686951ccc5395708356b461c0fc4efbe63fa4a0a97a317cdd486dfa3b4a6 0.600000000000 1505682 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": 1037161, "vin": [ { "gen": { "height": 1037151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1e3686951ccc5395708356b461c0fc4efbe63fa4a0a97a317cdd486dfa3b4a6" } } ], "extra": [ 1, 99, 124, 38, 178, 156, 114, 225, 200, 239, 159, 39, 178, 92, 195, 75, 190, 47, 144, 64, 79, 251, 71, 126, 137, 155, 189, 233, 175, 224, 197, 60, 100, 2, 17, 0, 0, 0, 1, 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