Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3631b2485e73b69d453bce04965c62139cfbca5e1f1e88399b28443b274d68a7

Tx prefix hash: 00b5885da4dc28a16373b27750ef125a2a9a53176adb339f9433747ab25cf189
Tx public key: a28b7b6c257584155975e438c47098a83ea1ead76b28ba611d09fb05b3095c42
Timestamp: 1725535426 Timestamp [UCT]: 2024-09-05 11:23:46 Age [y:d:h:m:s]: 00:213:23:55:06
Block: 1103453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152776 RingCT/type: yes/0
Extra: 01a28b7b6c257584155975e438c47098a83ea1ead76b28ba611d09fb05b3095c4202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a2c5620b715b957c6c0ea7dabf6d1445ee104ca634c7cc0d26fd97d8f4d565 0.600000000000 1580286 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": 1103463, "vin": [ { "gen": { "height": 1103453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a2c5620b715b957c6c0ea7dabf6d1445ee104ca634c7cc0d26fd97d8f4d565" } } ], "extra": [ 1, 162, 139, 123, 108, 37, 117, 132, 21, 89, 117, 228, 56, 196, 112, 152, 168, 62, 161, 234, 215, 107, 40, 186, 97, 29, 9, 251, 5, 179, 9, 92, 66, 2, 17, 0, 0, 0, 2, 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