Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 709ecfa2b48ff5c8b7351cd08069d64453272b998effdb88b4db2fe602234701

Tx prefix hash: 76b84c8eea263ea4f626472f7ff3c4e635a5f385de62793ada9d26b499df9a16
Tx public key: 3c56577aac8ff1cc8465d65ad8af00b8b4f01072af5d8e003b844c3a77c4c977
Timestamp: 1704054776 Timestamp [UCT]: 2023-12-31 20:32:56 Age [y:d:h:m:s]: 01:355:22:10:29
Block: 925355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513269 RingCT/type: yes/0
Extra: 013c56577aac8ff1cc8465d65ad8af00b8b4f01072af5d8e003b844c3a77c4c9770211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a860c00b237d809734ee5f4cbc61c16b364d962d927eda895af4fb35e2e0a793 0.600000000000 1383117 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": 925365, "vin": [ { "gen": { "height": 925355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a860c00b237d809734ee5f4cbc61c16b364d962d927eda895af4fb35e2e0a793" } } ], "extra": [ 1, 60, 86, 87, 122, 172, 143, 241, 204, 132, 101, 214, 90, 216, 175, 0, 184, 180, 240, 16, 114, 175, 93, 142, 0, 59, 132, 76, 58, 119, 196, 201, 119, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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