Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7f291a72f4c240f98b77786b86e11bc3a1afb35cf711c5299e70f5f934069bf

Tx prefix hash: 9852273fd206f72e411ba3de81fd141dac9edad2b0e6673a23bf11be31c9d53e
Tx public key: f45b09860ec1c7a0249d16cb3cf215c5387d91b7a4b23f9a3d23de8ae387927a
Timestamp: 1647801247 Timestamp [UCT]: 2022-03-20 18:34:07 Age [y:d:h:m:s]: 02:359:20:43:05
Block: 462700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776503 RingCT/type: yes/0
Extra: 01f45b09860ec1c7a0249d16cb3cf215c5387d91b7a4b23f9a3d23de8ae387927a02110000000ea8c141c5000000000000000000

1 output(s) for total of 17.984087091000 dcy

stealth address amount amount idx
00: a8b73613430c8ce754e9d045c6d6af839091e98fb6072d6df9f5a9ced4198769 17.984087091000 880201 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": 462710, "vin": [ { "gen": { "height": 462700 } } ], "vout": [ { "amount": 17984087091, "target": { "key": "a8b73613430c8ce754e9d045c6d6af839091e98fb6072d6df9f5a9ced4198769" } } ], "extra": [ 1, 244, 91, 9, 134, 14, 193, 199, 160, 36, 157, 22, 203, 60, 242, 21, 197, 56, 125, 145, 183, 164, 178, 63, 154, 61, 35, 222, 138, 227, 135, 146, 122, 2, 17, 0, 0, 0, 14, 168, 193, 65, 197, 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