Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f16fdb6fa2ee8d9cf250b56cc1c6272db898a42072fcb35d104f040595fb12

Tx prefix hash: e01c1c63c6414a0627198eb2956df139c7f830426cd45ade81c38c074757bdd6
Tx public key: e9cb39a064b57b5a335f8130365e1076b2e7443acca5ecda5bf4b13a0c252ade
Timestamp: 1713290901 Timestamp [UCT]: 2024-04-16 18:08:21 Age [y:d:h:m:s]: 00:212:05:56:11
Block: 1001912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151969 RingCT/type: yes/0
Extra: 01e9cb39a064b57b5a335f8130365e1076b2e7443acca5ecda5bf4b13a0c252ade0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30bd76849c8a42b06a2884c0e77f14d95c9af4566149151d5debf4c1bc7bfbb3 0.600000000000 1462426 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": 1001922, "vin": [ { "gen": { "height": 1001912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30bd76849c8a42b06a2884c0e77f14d95c9af4566149151d5debf4c1bc7bfbb3" } } ], "extra": [ 1, 233, 203, 57, 160, 100, 181, 123, 90, 51, 95, 129, 48, 54, 94, 16, 118, 178, 231, 68, 58, 204, 165, 236, 218, 91, 244, 177, 58, 12, 37, 42, 222, 2, 17, 0, 0, 0, 1, 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