Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 551d569df4a85ec38fb24e87aaed3ff921803cfbc9cbfcf58bb12656eb09cff3

Tx prefix hash: 8d062d52c6b7995a8f4e5d868ddfb43fa5e6b794d04c5d278591ee040573146c
Tx public key: 88aecd0a4f85fd9e9facc6742db4fcba28b4851dbc50bf6e2309c5595e607cab
Timestamp: 1715279223 Timestamp [UCT]: 2024-05-09 18:27:03 Age [y:d:h:m:s]: 01:182:13:30:37
Block: 1018421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389094 RingCT/type: yes/0
Extra: 0188aecd0a4f85fd9e9facc6742db4fcba28b4851dbc50bf6e2309c5595e607cab0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c211af0f1d8f92e1dff3dedee019767c683753dd19fd3356429d42f0f839323 0.600000000000 1482210 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": 1018431, "vin": [ { "gen": { "height": 1018421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c211af0f1d8f92e1dff3dedee019767c683753dd19fd3356429d42f0f839323" } } ], "extra": [ 1, 136, 174, 205, 10, 79, 133, 253, 158, 159, 172, 198, 116, 45, 180, 252, 186, 40, 180, 133, 29, 188, 80, 191, 110, 35, 9, 197, 89, 94, 96, 124, 171, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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