Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250327ab6c370c7cd31d61a823e1d4985feb60d8142df2246c4db032648d5cac

Tx prefix hash: 437c8356b90486663f93c9e60433fa99baafc4c5f1413cd6150e2ab249e2f944
Tx public key: ffd1c11f9930f08309d62e96774bda4b3c4653e8289bf883f189a99e15596815
Timestamp: 1714856367 Timestamp [UCT]: 2024-05-04 20:59:27 Age [y:d:h:m:s]: 00:249:16:16:15
Block: 1014921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178703 RingCT/type: yes/0
Extra: 01ffd1c11f9930f08309d62e96774bda4b3c4653e8289bf883f189a99e1559681502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72f877806d6a8e525620dbc4cd3058dbd2ca281d2b770dd83e9e40ea95919b0e 0.600000000000 1478144 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": 1014931, "vin": [ { "gen": { "height": 1014921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72f877806d6a8e525620dbc4cd3058dbd2ca281d2b770dd83e9e40ea95919b0e" } } ], "extra": [ 1, 255, 209, 193, 31, 153, 48, 240, 131, 9, 214, 46, 150, 119, 75, 218, 75, 60, 70, 83, 232, 40, 155, 248, 131, 241, 137, 169, 158, 21, 89, 104, 21, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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