Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd83d61e617ad3a98cf51b99d9f5378782b145188fc171ff4aaa57448622271

Tx prefix hash: ac6830b26a5884e204e597a011e35c113e9f6a9ff6ed7cc2c0b9d3ac9a5dc0db
Tx public key: 2c297f72bcd5df9bdd4ae27801b99811aa6b01f7efb7bda5b0612c7414892fa1
Timestamp: 1734592921 Timestamp [UCT]: 2024-12-19 07:22:01 Age [y:d:h:m:s]: 00:338:19:39:17
Block: 1178447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239658 RingCT/type: yes/0
Extra: 012c297f72bcd5df9bdd4ae27801b99811aa6b01f7efb7bda5b0612c7414892fa1021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d37e9745e9c7d9115248736265bd6b179f28457c6825f19f99b20530fafef5f9 0.600000000000 1664834 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": 1178457, "vin": [ { "gen": { "height": 1178447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d37e9745e9c7d9115248736265bd6b179f28457c6825f19f99b20530fafef5f9" } } ], "extra": [ 1, 44, 41, 127, 114, 188, 213, 223, 155, 221, 74, 226, 120, 1, 185, 152, 17, 170, 107, 1, 247, 239, 183, 189, 165, 176, 97, 44, 116, 20, 137, 47, 161, 2, 17, 0, 0, 0, 5, 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