Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a6f20388b2552788614c4a97d5f4b91c5000624d935ac0baa89b87cc83acaf4

Tx prefix hash: 536c244c7d74e086599ed9b78f771b146d3cebb6275cc7d4e046a23170a6aac0
Tx public key: a8d80d32dde36068949f9a490aa4c686f0d4b9a55cf4405f681b3a01a0ec30bb
Timestamp: 1723624358 Timestamp [UCT]: 2024-08-14 08:32:38 Age [y:d:h:m:s]: 00:232:17:08:08
Block: 1087612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166181 RingCT/type: yes/0
Extra: 01a8d80d32dde36068949f9a490aa4c686f0d4b9a55cf4405f681b3a01a0ec30bb02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83f63e6132fc2cd72658ad2e5c57ed2140f00be80be1afbbabfdb7dae1cde3bf 0.600000000000 1562221 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": 1087622, "vin": [ { "gen": { "height": 1087612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83f63e6132fc2cd72658ad2e5c57ed2140f00be80be1afbbabfdb7dae1cde3bf" } } ], "extra": [ 1, 168, 216, 13, 50, 221, 227, 96, 104, 148, 159, 154, 73, 10, 164, 198, 134, 240, 212, 185, 165, 92, 244, 64, 95, 104, 27, 58, 1, 160, 236, 48, 187, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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