Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32493bdb37f2c44a47c3038fe3a470c2b15f0c5b5a94e69ffbe3f60c279e0e03

Tx prefix hash: c5a3b3faa67d313d5ab9067c4d2e35d789ad4f9165d895a84842a5d65f9ff575
Tx public key: 211cfc9b4216e1cb7439280759cb6c18b8381bf8732ad826f1a15546a10fd318
Timestamp: 1633207079 Timestamp [UCT]: 2021-10-02 20:37:59 Age [y:d:h:m:s]: 04:033:03:54:15
Block: 345380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1059043 RingCT/type: yes/0
Extra: 01211cfc9b4216e1cb7439280759cb6c18b8381bf8732ad826f1a15546a10fd31802110000001afdc024ec000000000000000000

1 output(s) for total of 44.016257695000 dcy

stealth address amount amount idx
00: 46bdba0f32628ceebadc203cbcc0ed1ce7c3e8c0bce109958591ab44a3bd73aa 44.016257695000 708526 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": 345390, "vin": [ { "gen": { "height": 345380 } } ], "vout": [ { "amount": 44016257695, "target": { "key": "46bdba0f32628ceebadc203cbcc0ed1ce7c3e8c0bce109958591ab44a3bd73aa" } } ], "extra": [ 1, 33, 28, 252, 155, 66, 22, 225, 203, 116, 57, 40, 7, 89, 203, 108, 24, 184, 56, 27, 248, 115, 42, 216, 38, 241, 161, 85, 70, 161, 15, 211, 24, 2, 17, 0, 0, 0, 26, 253, 192, 36, 236, 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