Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aa22fb90e7ce07f72d125967f475f53e430ad4ce6ac03f13c827752425b97da

Tx prefix hash: bc75a5077ed39a218a04724e1ac5217d20e286cb92cf9341f38507a8f99ccc8b
Tx public key: d4cb46d6fa9a14cb784a2ee6c54a3eb1fcbd0ed2e6453fcc6b91eef1b2716e5f
Timestamp: 1681516764 Timestamp [UCT]: 2023-04-14 23:59:24 Age [y:d:h:m:s]: 02:005:11:20:21
Block: 738747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526069 RingCT/type: yes/0
Extra: 01d4cb46d6fa9a14cb784a2ee6c54a3eb1fcbd0ed2e6453fcc6b91eef1b2716e5f0211000000015029cbac000000000000000000

1 output(s) for total of 2.188894047000 dcy

stealth address amount amount idx
00: c78b994174b09b7c9b41bc7b278afdbeaf1f49116bdd2c8dafa0c8600acf56c3 2.188894047000 1185494 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": 738757, "vin": [ { "gen": { "height": 738747 } } ], "vout": [ { "amount": 2188894047, "target": { "key": "c78b994174b09b7c9b41bc7b278afdbeaf1f49116bdd2c8dafa0c8600acf56c3" } } ], "extra": [ 1, 212, 203, 70, 214, 250, 154, 20, 203, 120, 74, 46, 230, 197, 74, 62, 177, 252, 189, 14, 210, 230, 69, 63, 204, 107, 145, 238, 241, 178, 113, 110, 95, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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