Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83660881dce63167a3b65488ccdc97d592ef7716824124d7df81329d15a3429c

Tx prefix hash: 9c902e28b35a7f0ad3cf75d533a1bc2ee928529f9c0713d4a9ca56aa0bc22d04
Tx public key: b1692a3f0a8b3ed5cd1971c9d84408ad159137533fa3ac87143a06a6f133d0b1
Timestamp: 1699588164 Timestamp [UCT]: 2023-11-10 03:49:24 Age [y:d:h:m:s]: 01:082:22:29:15
Block: 888336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320429 RingCT/type: yes/0
Extra: 01b1692a3f0a8b3ed5cd1971c9d84408ad159137533fa3ac87143a06a6f133d0b102110000000133af99f4000000000000000000

1 output(s) for total of 0.699155964000 dcy

stealth address amount amount idx
00: f949795daa5f45a0b741404b8de3b9e391cb04e63fe4f9cc1694497d67023d8d 0.699155964000 1344275 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": 888346, "vin": [ { "gen": { "height": 888336 } } ], "vout": [ { "amount": 699155964, "target": { "key": "f949795daa5f45a0b741404b8de3b9e391cb04e63fe4f9cc1694497d67023d8d" } } ], "extra": [ 1, 177, 105, 42, 63, 10, 139, 62, 213, 205, 25, 113, 201, 216, 68, 8, 173, 21, 145, 55, 83, 63, 163, 172, 135, 20, 58, 6, 166, 241, 51, 208, 177, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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