Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b266a90664d6950112a1229bbfa815ed96e9af4a7900c7dc7baca287178345e

Tx prefix hash: 4a3891c87a5beee30b15d5b535d3a5bb4896fbb30c05d086c8dd768021518a27
Tx public key: ea7af082cf4eb422a07d835a5298ca0f52247847293174f032fc34c14c094160
Timestamp: 1688839877 Timestamp [UCT]: 2023-07-08 18:11:17 Age [y:d:h:m:s]: 01:194:14:40:14
Block: 799490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400434 RingCT/type: yes/0
Extra: 01ea7af082cf4eb422a07d835a5298ca0f52247847293174f032fc34c14c09416002110000000575e3f0e9000000000000000000

1 output(s) for total of 1.377075896000 dcy

stealth address amount amount idx
00: 7953d5f5b46aa96cc35f947cc6b51279bf7c97e4a1a4e1e0a71ef2b03a4e73b5 1.377075896000 1250507 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": 799500, "vin": [ { "gen": { "height": 799490 } } ], "vout": [ { "amount": 1377075896, "target": { "key": "7953d5f5b46aa96cc35f947cc6b51279bf7c97e4a1a4e1e0a71ef2b03a4e73b5" } } ], "extra": [ 1, 234, 122, 240, 130, 207, 78, 180, 34, 160, 125, 131, 90, 82, 152, 202, 15, 82, 36, 120, 71, 41, 49, 116, 240, 50, 252, 52, 193, 76, 9, 65, 96, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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