Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c36f535471b3df2f467bbaf3dbc00ea86bd2249d9e06909767350336743b5a

Tx prefix hash: 9a755a0e420f8676797c9ac4d65d159278318c2dce818d150517156254f0851a
Tx public key: 0f8e302a94cf1383db4ddc57d2d57822ebe3949ce2a3b81f70a73c468c30c456
Timestamp: 1716301295 Timestamp [UCT]: 2024-05-21 14:21:35 Age [y:d:h:m:s]: 00:281:00:42:32
Block: 1026898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200830 RingCT/type: yes/0
Extra: 010f8e302a94cf1383db4ddc57d2d57822ebe3949ce2a3b81f70a73c468c30c4560211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9b656c535a3cd433d79ad75b3a18117edf218de49f93a61ea00ed5ea45384a2 0.600000000000 1494233 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": 1026908, "vin": [ { "gen": { "height": 1026898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9b656c535a3cd433d79ad75b3a18117edf218de49f93a61ea00ed5ea45384a2" } } ], "extra": [ 1, 15, 142, 48, 42, 148, 207, 19, 131, 219, 77, 220, 87, 210, 213, 120, 34, 235, 227, 148, 156, 226, 163, 184, 31, 112, 167, 60, 70, 140, 48, 196, 86, 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