Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13fdfc5aafef5e6e9d6759803c00c1041311f114037d1f3788aa655dd4d855cf

Tx prefix hash: 15be6e6c0f9bdc6bdb5534b4d47f6d018f7bebd45a57946f1bdf2f8453fe7474
Tx public key: e9f8483d0e1550af03f28cc037474fa0c32eb44e72224ebdc181a69367b130b0
Timestamp: 1584857996 Timestamp [UCT]: 2020-03-22 06:19:56 Age [y:d:h:m:s]: 04:238:16:18:05
Block: 86463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067369 RingCT/type: yes/0
Extra: 01e9f8483d0e1550af03f28cc037474fa0c32eb44e72224ebdc181a69367b130b00211000000644ac5aa02000000000000000000

1 output(s) for total of 317.331342447000 dcy

stealth address amount amount idx
00: 1be9ccf0527d79ab1b2cd81f670a665aeff39c72d6a3f0400d728a3940836d6d 317.331342447000 156013 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": 86473, "vin": [ { "gen": { "height": 86463 } } ], "vout": [ { "amount": 317331342447, "target": { "key": "1be9ccf0527d79ab1b2cd81f670a665aeff39c72d6a3f0400d728a3940836d6d" } } ], "extra": [ 1, 233, 248, 72, 61, 14, 21, 80, 175, 3, 242, 140, 192, 55, 71, 79, 160, 195, 46, 180, 78, 114, 34, 78, 189, 193, 129, 166, 147, 103, 177, 48, 176, 2, 17, 0, 0, 0, 100, 74, 197, 170, 2, 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