Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a30593f9528b115b755eb55ab2fb0864e184864728b051a56d9e802d2c32def

Tx prefix hash: be8325fcaa95707c56e79adbbde8483cb99aaf9f6bfd913e56d7574508f73d9d
Tx public key: 7e608b7f234062b518b62c81fa91e5dee57d248ca7edb0177f9af97767473f3a
Timestamp: 1709660766 Timestamp [UCT]: 2024-03-05 17:46:06 Age [y:d:h:m:s]: 01:060:13:32:41
Block: 971841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304303 RingCT/type: yes/0
Extra: 017e608b7f234062b518b62c81fa91e5dee57d248ca7edb0177f9af97767473f3a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd17417391d7a8db3cce94aa7bec1227f755fc9e2f2a6372b7f77fd4c3637071 0.600000000000 1431744 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": 971851, "vin": [ { "gen": { "height": 971841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd17417391d7a8db3cce94aa7bec1227f755fc9e2f2a6372b7f77fd4c3637071" } } ], "extra": [ 1, 126, 96, 139, 127, 35, 64, 98, 181, 24, 182, 44, 129, 250, 145, 229, 222, 229, 125, 36, 140, 167, 237, 176, 23, 127, 154, 249, 119, 103, 71, 63, 58, 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