Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f7e6bac84f2d7ba27848aaa635494159302a0c7e16dc3aa067f2a6a6b9b95b

Tx prefix hash: cfb002d704a95bb6f5a70f3c5b0b988ecc03a95e1b0957e8ae8d914e6f8ca3b8
Tx public key: 45b75f43cd86aaed486c8c56a954d523306c5bfa008f8138adc5cc18d94711a2
Timestamp: 1674972887 Timestamp [UCT]: 2023-01-29 06:14:47 Age [y:d:h:m:s]: 01:349:12:41:42
Block: 685131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510800 RingCT/type: yes/0
Extra: 0145b75f43cd86aaed486c8c56a954d523306c5bfa008f8138adc5cc18d94711a20211000000035029cbac000000000000000000

1 output(s) for total of 3.295160103000 dcy

stealth address amount amount idx
00: 4b94149b43a2bdc3c59746fb2c3f94add4c7417a71eca0f37f36378f9b7938f4 3.295160103000 1127420 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": 685141, "vin": [ { "gen": { "height": 685131 } } ], "vout": [ { "amount": 3295160103, "target": { "key": "4b94149b43a2bdc3c59746fb2c3f94add4c7417a71eca0f37f36378f9b7938f4" } } ], "extra": [ 1, 69, 183, 95, 67, 205, 134, 170, 237, 72, 108, 140, 86, 169, 84, 213, 35, 48, 108, 91, 250, 0, 143, 129, 56, 173, 197, 204, 24, 217, 71, 17, 162, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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