Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f961e0ef4df922d320623f768438c64c40162e8c3249bca7a4925fefad3af684

Tx prefix hash: 68b848560c2e014a356bf662c2d74dd6c6c4d4b417127641d0d60c59a36b7a33
Tx public key: e622b105f1784d2437b75abfd975e189560f4fc316d4141ca42457d7c539a507
Timestamp: 1672246832 Timestamp [UCT]: 2022-12-28 17:00:32 Age [y:d:h:m:s]: 02:111:14:21:44
Block: 662506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601483 RingCT/type: yes/0
Extra: 01e622b105f1784d2437b75abfd975e189560f4fc316d4141ca42457d7c539a507021100000001e7ace25d000000000000000000

1 output(s) for total of 3.915998988000 dcy

stealth address amount amount idx
00: 0ba135ab47cce46b68d9da8d0c0927a66ec4b2dbed423e9a527b79182bf2d1eb 3.915998988000 1103359 of 0

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": 662516, "vin": [ { "gen": { "height": 662506 } } ], "vout": [ { "amount": 3915998988, "target": { "key": "0ba135ab47cce46b68d9da8d0c0927a66ec4b2dbed423e9a527b79182bf2d1eb" } } ], "extra": [ 1, 230, 34, 177, 5, 241, 120, 77, 36, 55, 183, 90, 191, 217, 117, 225, 137, 86, 15, 79, 195, 22, 212, 20, 28, 164, 36, 87, 215, 197, 57, 165, 7, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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