Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 426cdbfa34b4f443f61a6c850862fff1c6a4d0e74153c2bc812bd371fb51bd78

Tx prefix hash: c91051fccd76bcfc1c2e8fb0170dd5bc2cd7a2625abde542e42696bd952c7e0a
Tx public key: 099b434df84967fa368ea495d3e67cb37ac496c29457f943abd7666f9cfb4586
Timestamp: 1713357292 Timestamp [UCT]: 2024-04-17 12:34:52 Age [y:d:h:m:s]: 00:269:19:07:37
Block: 1002485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193109 RingCT/type: yes/0
Extra: 01099b434df84967fa368ea495d3e67cb37ac496c29457f943abd7666f9cfb458602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6961a2ec7157dd3b5a7391d7399a5e5a6fa42e3eab882e9c74304f071ddcaa0a 0.600000000000 1463001 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": 1002495, "vin": [ { "gen": { "height": 1002485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6961a2ec7157dd3b5a7391d7399a5e5a6fa42e3eab882e9c74304f071ddcaa0a" } } ], "extra": [ 1, 9, 155, 67, 77, 248, 73, 103, 250, 54, 142, 164, 149, 211, 230, 124, 179, 122, 196, 150, 194, 148, 87, 249, 67, 171, 215, 102, 111, 156, 251, 69, 134, 2, 17, 0, 0, 0, 4, 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