Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 262836042810dcf3da0086b5a5684ab8734b86222587b566581cf85e1f8a043d

Tx prefix hash: 7866972d9519a22062647d6cdbcf53645e4467e6680cc7eaf240a4a23cfe4618
Tx public key: c29aa862ccd8fca4cdb13baa336f4c906c2b2b3dd347e98adf38519b3d53b226
Timestamp: 1736586687 Timestamp [UCT]: 2025-01-11 09:11:27 Age [y:d:h:m:s]: 00:112:13:54:36
Block: 1194934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80243 RingCT/type: yes/0
Extra: 01c29aa862ccd8fca4cdb13baa336f4c906c2b2b3dd347e98adf38519b3d53b2260211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbe0c7da3e03ed631cd0ea53493649addc0ee0bbde678499d8ae85d6333777db 0.600000000000 1681513 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": 1194944, "vin": [ { "gen": { "height": 1194934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbe0c7da3e03ed631cd0ea53493649addc0ee0bbde678499d8ae85d6333777db" } } ], "extra": [ 1, 194, 154, 168, 98, 204, 216, 252, 164, 205, 177, 59, 170, 51, 111, 76, 144, 108, 43, 43, 61, 211, 71, 233, 138, 223, 56, 81, 155, 61, 83, 178, 38, 2, 17, 0, 0, 0, 6, 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