Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41cb18ba5ceafcd0c3139b3ca1d327c0b005916c7fd29ca30bf7f59f451e9b35

Tx prefix hash: 202b05b21fa79ae22a3fd0414420f0eb594120f2518a0a3d7f67a00bd81712f9
Tx public key: a896cf3f98bdb70f822024b5f857074a196ae7e9d9c35f8fa8c688629c686d54
Timestamp: 1648625373 Timestamp [UCT]: 2022-03-30 07:29:33 Age [y:d:h:m:s]: 02:242:06:49:51
Block: 469423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692750 RingCT/type: yes/0
Extra: 01a896cf3f98bdb70f822024b5f857074a196ae7e9d9c35f8fa8c688629c686d5402110000001237cb3088000000000000000000

1 output(s) for total of 17.084685341000 dcy

stealth address amount amount idx
00: 8ec28bcc86c7a8244c08c013a621b42689e135e2f353cd274aebdc828d6e0376 17.084685341000 888367 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": 469433, "vin": [ { "gen": { "height": 469423 } } ], "vout": [ { "amount": 17084685341, "target": { "key": "8ec28bcc86c7a8244c08c013a621b42689e135e2f353cd274aebdc828d6e0376" } } ], "extra": [ 1, 168, 150, 207, 63, 152, 189, 183, 15, 130, 32, 36, 181, 248, 87, 7, 74, 25, 106, 231, 233, 217, 195, 95, 143, 168, 198, 136, 98, 156, 104, 109, 84, 2, 17, 0, 0, 0, 18, 55, 203, 48, 136, 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