Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71a24a34bb0545dcc5d4f172220486953da8a7b4cbd54277715f6915e2dfcd52

Tx prefix hash: 970d9d5d39c63ae455ce056fed1f7aac0ad2afea4ff7d0254f03ea04848f3b08
Tx public key: 4177c61d0fde7d5ee04833b04e68f3cccd52004c16f2baec06cb46a705d08b08
Timestamp: 1732034091 Timestamp [UCT]: 2024-11-19 16:34:51 Age [y:d:h:m:s]: 01:001:05:44:56
Block: 1157237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259292 RingCT/type: yes/0
Extra: 014177c61d0fde7d5ee04833b04e68f3cccd52004c16f2baec06cb46a705d08b08021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da8f1b49b1500aa967151f56717a686da6529c389f8efed40df271f41105d6d3 0.600000000000 1642860 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": 1157247, "vin": [ { "gen": { "height": 1157237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da8f1b49b1500aa967151f56717a686da6529c389f8efed40df271f41105d6d3" } } ], "extra": [ 1, 65, 119, 198, 29, 15, 222, 125, 94, 224, 72, 51, 176, 78, 104, 243, 204, 205, 82, 0, 76, 22, 242, 186, 236, 6, 203, 70, 167, 5, 208, 139, 8, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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