Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ea0a261ae8358ee49ea2d3d1be6d921b6c03965f131240d36d1ff33d36de2a

Tx prefix hash: 422167d3db2c3d91edd36140df1a77188848d44e5700fbf87ddbdb9281b7e304
Tx public key: 1ef226b6955cf5779d6863db7231ed8cc071bb46c6b73ff6d8cdf064ef8d8629
Timestamp: 1738541808 Timestamp [UCT]: 2025-02-03 00:16:48 Age [y:d:h:m:s]: 00:291:23:14:16
Block: 1210835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206445 RingCT/type: yes/0
Extra: 011ef226b6955cf5779d6863db7231ed8cc071bb46c6b73ff6d8cdf064ef8d86290211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48558421a6e710b307be1068fe426b0024f09c02f232a1dcb1d12d27d7f6fba4 0.600000000000 1697590 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": 1210845, "vin": [ { "gen": { "height": 1210835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48558421a6e710b307be1068fe426b0024f09c02f232a1dcb1d12d27d7f6fba4" } } ], "extra": [ 1, 30, 242, 38, 182, 149, 92, 245, 119, 157, 104, 99, 219, 114, 49, 237, 140, 192, 113, 187, 70, 198, 183, 63, 246, 216, 205, 240, 100, 239, 141, 134, 41, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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