Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4196d52aaf0ff7dddc6d612efa14773d2aced2c7dd54810e09a8788af59ed725

Tx prefix hash: 9fbf568ddca78fa866241f5c8e511821a959722ded1e6fe13e23e14fe6156f1c
Tx public key: 8866bdeb0439b20c5c7b343b4ada9345f2509a1aaa22e4e937f2e1e04e79a8e3
Timestamp: 1727723330 Timestamp [UCT]: 2024-09-30 19:08:50 Age [y:d:h:m:s]: 00:102:06:49:01
Block: 1121587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73117 RingCT/type: yes/0
Extra: 018866bdeb0439b20c5c7b343b4ada9345f2509a1aaa22e4e937f2e1e04e79a8e302110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e57a033bd0f9b267347102c6a51b5890a8544592fe67efdb9fae65af7944fcbb 0.600000000000 1603882 of 15

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": 1121597, "vin": [ { "gen": { "height": 1121587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e57a033bd0f9b267347102c6a51b5890a8544592fe67efdb9fae65af7944fcbb" } } ], "extra": [ 1, 136, 102, 189, 235, 4, 57, 178, 12, 92, 123, 52, 59, 74, 218, 147, 69, 242, 80, 154, 26, 170, 34, 228, 233, 55, 242, 225, 224, 78, 121, 168, 227, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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