Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af79f1683105d7fefd3b6f3d23a28ae04fe826893a6117c5941711a36c72f5a6

Tx prefix hash: 53571872eb12b90b09eaeb2ba21ba40fd5a67d4c2d84c268e27d4e38d37170e3
Tx public key: f4c18bf08542e118cd409280520c8570ba40e3b0b263560feebd3a28915ff55c
Timestamp: 1663775556 Timestamp [UCT]: 2022-09-21 15:52:36 Age [y:d:h:m:s]: 02:186:02:36:33
Block: 592755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 654393 RingCT/type: yes/0
Extra: 01f4c18bf08542e118cd409280520c8570ba40e3b0b263560feebd3a28915ff55c021100000003e6d27f9c000000000000000000

1 output(s) for total of 6.667402769000 dcy

stealth address amount amount idx
00: c2eab7ca6762c45bb58cf5204dd28ec61047b7a23e695a04d7b3807b89e2824b 6.667402769000 1027446 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": 592765, "vin": [ { "gen": { "height": 592755 } } ], "vout": [ { "amount": 6667402769, "target": { "key": "c2eab7ca6762c45bb58cf5204dd28ec61047b7a23e695a04d7b3807b89e2824b" } } ], "extra": [ 1, 244, 193, 139, 240, 133, 66, 225, 24, 205, 64, 146, 128, 82, 12, 133, 112, 186, 64, 227, 176, 178, 99, 86, 15, 238, 189, 58, 40, 145, 95, 245, 92, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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