Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fccded14592081c1723da1d9b1396baca8d99be8d61fc9f5128c32fb4901179

Tx prefix hash: c52ea1e12164e3a3c80537bc41b60044ae8644ce057161e73d8b6668c5b54aef
Tx public key: 041100060a4a3ee980f9bcb742da185e1b54c4500489ff06d4a3bae55a67a1f7
Timestamp: 1655883575 Timestamp [UCT]: 2022-06-22 07:39:35 Age [y:d:h:m:s]: 03:131:23:14:16
Block: 527775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 873987 RingCT/type: yes/0
Extra: 01041100060a4a3ee980f9bcb742da185e1b54c4500489ff06d4a3bae55a67a1f702110000000575e3f0e9000000000000000000

1 output(s) for total of 10.946177847000 dcy

stealth address amount amount idx
00: 0db7b2ec7b81d919fa878b90866ddbe017b63aae5e80ca62f16357309f9c5873 10.946177847000 956496 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": 527785, "vin": [ { "gen": { "height": 527775 } } ], "vout": [ { "amount": 10946177847, "target": { "key": "0db7b2ec7b81d919fa878b90866ddbe017b63aae5e80ca62f16357309f9c5873" } } ], "extra": [ 1, 4, 17, 0, 6, 10, 74, 62, 233, 128, 249, 188, 183, 66, 218, 24, 94, 27, 84, 196, 80, 4, 137, 255, 6, 212, 163, 186, 229, 90, 103, 161, 247, 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