Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f0e71021d20edf50f3fe6d4b844f8bb9ded77b32dee29e40cab47eec2d0569e

Tx prefix hash: 15b018e0b7e9d59edb49a889a4898c22563a00f3661149fc85763706255e6ba2
Tx public key: 5b0d6559a6e69edc016e8726fe6585ce9837be1902d8108b492b4c8dcbc5cb30
Timestamp: 1702535741 Timestamp [UCT]: 2023-12-14 06:35:41 Age [y:d:h:m:s]: 01:327:10:05:41
Block: 912768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492844 RingCT/type: yes/0
Extra: 015b0d6559a6e69edc016e8726fe6585ce9837be1902d8108b492b4c8dcbc5cb3002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb6458965e932bc1e23caccda5ff32a2c230a134fc83a4f8e3425bb19f6105b5 0.600000000000 1370004 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": 912778, "vin": [ { "gen": { "height": 912768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb6458965e932bc1e23caccda5ff32a2c230a134fc83a4f8e3425bb19f6105b5" } } ], "extra": [ 1, 91, 13, 101, 89, 166, 230, 158, 220, 1, 110, 135, 38, 254, 101, 133, 206, 152, 55, 190, 25, 2, 216, 16, 139, 73, 43, 76, 141, 203, 197, 203, 48, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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