Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80607c27339717eedf767b1226c293e3550a82eb4753b74109b80b7b20ea49c7

Tx prefix hash: a0a7b61673c92dd925327d9483c9f7d7276df5c1fd7c7624f2ce19397497117f
Tx public key: 621f31e3bf146ec40e399b25d04c4eec1eee3d2e03b0100124727a1e56e0d773
Timestamp: 1734205841 Timestamp [UCT]: 2024-12-14 19:50:41 Age [y:d:h:m:s]: 00:124:22:15:54
Block: 1175243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89066 RingCT/type: yes/0
Extra: 01621f31e3bf146ec40e399b25d04c4eec1eee3d2e03b0100124727a1e56e0d773021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e8d593397df37a82ec6eaf645107822941629919cfbdb49daf09fc94e4b2454 0.600000000000 1661496 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": 1175253, "vin": [ { "gen": { "height": 1175243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e8d593397df37a82ec6eaf645107822941629919cfbdb49daf09fc94e4b2454" } } ], "extra": [ 1, 98, 31, 49, 227, 191, 20, 110, 196, 14, 57, 155, 37, 208, 76, 78, 236, 30, 238, 61, 46, 3, 176, 16, 1, 36, 114, 122, 30, 86, 224, 215, 115, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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