Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9696bac32eacde99ec676bbf2080d3ca3ab721a536cb6e77031e6694ddfb1b9

Tx prefix hash: e17e0c7660a03ff49bbef7b1f7948d3cf6ce534f184b13cb1696ac98c546d460
Tx public key: 787e798262ce75103f3325c8421a784c78a7d2a7438ccf8cd60d0fd021bb7e92
Timestamp: 1732156376 Timestamp [UCT]: 2024-11-21 02:32:56 Age [y:d:h:m:s]: 00:158:12:26:34
Block: 1158240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113134 RingCT/type: yes/0
Extra: 01787e798262ce75103f3325c8421a784c78a7d2a7438ccf8cd60d0fd021bb7e920211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c87d9a1c8aeb0a9d3f87c1be8c29df14c21622bc7649f29a484d37c64b46256f 0.600000000000 1643869 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": 1158250, "vin": [ { "gen": { "height": 1158240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c87d9a1c8aeb0a9d3f87c1be8c29df14c21622bc7649f29a484d37c64b46256f" } } ], "extra": [ 1, 120, 126, 121, 130, 98, 206, 117, 16, 63, 51, 37, 200, 66, 26, 120, 76, 120, 167, 210, 167, 67, 140, 207, 140, 214, 13, 15, 208, 33, 187, 126, 146, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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