Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41e5721636ecaf149a3c36aa6a2bed5c062914b8c02a05f7180525d4dc71bfd3

Tx prefix hash: 526aae71038038d34e345fb3a088eaeda393b3f327091612c6047169f33ae195
Tx public key: 4d5006f2b5aad72ed23525e52c7a87f5d9ca0f5ee271140280b173c5d93adff4
Timestamp: 1576643734 Timestamp [UCT]: 2019-12-18 04:35:34 Age [y:d:h:m:s]: 05:077:15:40:28
Block: 28372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203096 RingCT/type: yes/0
Extra: 014d5006f2b5aad72ed23525e52c7a87f5d9ca0f5ee271140280b173c5d93adff4021100000011ad433a0b000000000000000000

1 output(s) for total of 494.302322359000 dcy

stealth address amount amount idx
00: 309a972d58e4e0de208510c03fa0d19827ade87835b275440ca5e6be64a38127 494.302322359000 46916 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": 28382, "vin": [ { "gen": { "height": 28372 } } ], "vout": [ { "amount": 494302322359, "target": { "key": "309a972d58e4e0de208510c03fa0d19827ade87835b275440ca5e6be64a38127" } } ], "extra": [ 1, 77, 80, 6, 242, 181, 170, 215, 46, 210, 53, 37, 229, 44, 122, 135, 245, 217, 202, 15, 94, 226, 113, 20, 2, 128, 177, 115, 197, 217, 58, 223, 244, 2, 17, 0, 0, 0, 17, 173, 67, 58, 11, 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