Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bce5ee2287f158eb9b2af077f01d1609b7f907f14be20fdf4fb39ddf30957bac

Tx prefix hash: d88c4d7c3d6e53e85425fc631c0d6b12d46aa80b890dbdbccddca0c53a5031a9
Tx public key: 34b1d2f78cef5353cd591f86d7e0472987415e9921fa1d215fa71cb4b9cd66cd
Timestamp: 1698955067 Timestamp [UCT]: 2023-11-02 19:57:47 Age [y:d:h:m:s]: 02:007:23:43:06
Block: 883293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525290 RingCT/type: yes/0
Extra: 0134b1d2f78cef5353cd591f86d7e0472987415e9921fa1d215fa71cb4b9cd66cd02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.726580313000 dcy

stealth address amount amount idx
00: 27a1f1193ce02f620e47e58f4fa59728d96261afa4f25e8a91259b4e1d22c73b 0.726580313000 1338985 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": 883303, "vin": [ { "gen": { "height": 883293 } } ], "vout": [ { "amount": 726580313, "target": { "key": "27a1f1193ce02f620e47e58f4fa59728d96261afa4f25e8a91259b4e1d22c73b" } } ], "extra": [ 1, 52, 177, 210, 247, 140, 239, 83, 83, 205, 89, 31, 134, 215, 224, 71, 41, 135, 65, 94, 153, 33, 250, 29, 33, 95, 167, 28, 180, 185, 205, 102, 205, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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