Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea75f30127ffdc4fc33e5fa16e80974b1e174fff93e7b7a2875d1556e87bc435

Tx prefix hash: 8bea60ae04387d2d61b6d02217a8c15a016aeb2b8164f1f547644bccb1f023ba
Tx public key: f2289a60eabd7edbecfa4c0276ef2fa29853233d915d8ef25acc25cd5c72ea13
Timestamp: 1713317869 Timestamp [UCT]: 2024-04-17 01:37:49 Age [y:d:h:m:s]: 01:049:13:58:46
Block: 1002141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296440 RingCT/type: yes/0
Extra: 01f2289a60eabd7edbecfa4c0276ef2fa29853233d915d8ef25acc25cd5c72ea1302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77fd3becd783c7c2eb5f1aeda0d0d6ec7bdae911848c43168fb9c442707a5c93 0.600000000000 1462657 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": 1002151, "vin": [ { "gen": { "height": 1002141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77fd3becd783c7c2eb5f1aeda0d0d6ec7bdae911848c43168fb9c442707a5c93" } } ], "extra": [ 1, 242, 40, 154, 96, 234, 189, 126, 219, 236, 250, 76, 2, 118, 239, 47, 162, 152, 83, 35, 61, 145, 93, 142, 242, 90, 204, 37, 205, 92, 114, 234, 19, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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