Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68071412fd1ef7059b5e84d92c6bbe013c80f3bf32f0e50fd9c522fd7e9e0102

Tx prefix hash: 2f6d7d2b335e20c2a9fd4c1ea98eec3aefe86aa4d41deda871f9b2a8b242c1a3
Tx public key: d226fda279214eac1fd79a215227181f64a55752422fb7671c36baf60be92e19
Timestamp: 1727365733 Timestamp [UCT]: 2024-09-26 15:48:53 Age [y:d:h:m:s]: 00:058:21:52:38
Block: 1118618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42104 RingCT/type: yes/0
Extra: 01d226fda279214eac1fd79a215227181f64a55752422fb7671c36baf60be92e19021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c296164b693db681472689c8fb4d53d8e8294712f34fd8d9ac64b2b62e383ad 0.600000000000 1599875 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": 1118628, "vin": [ { "gen": { "height": 1118618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c296164b693db681472689c8fb4d53d8e8294712f34fd8d9ac64b2b62e383ad" } } ], "extra": [ 1, 210, 38, 253, 162, 121, 33, 78, 172, 31, 215, 154, 33, 82, 39, 24, 31, 100, 165, 87, 82, 66, 47, 183, 103, 28, 54, 186, 246, 11, 233, 46, 25, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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