Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86bde61801827c4e0fd1107b8ba97904029d1d42c1445dbe53c79df6ba83abb1

Tx prefix hash: de6d18758d131467114ed47ff1b447b4b872d2c9437162f7f108e4c72bf0632d
Tx public key: 249efd03b03d8893fb2bc71b8c2a05c72396c9d41a9bde9eb4500928467d47d6
Timestamp: 1720774365 Timestamp [UCT]: 2024-07-12 08:52:45 Age [y:d:h:m:s]: 00:265:17:09:48
Block: 1063987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189815 RingCT/type: yes/0
Extra: 01249efd03b03d8893fb2bc71b8c2a05c72396c9d41a9bde9eb4500928467d47d602110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8fce1ec00f78536ca7690e7853d85bc94c68ad2efa804e8352eb0940a5bf957 0.600000000000 1534508 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": 1063997, "vin": [ { "gen": { "height": 1063987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8fce1ec00f78536ca7690e7853d85bc94c68ad2efa804e8352eb0940a5bf957" } } ], "extra": [ 1, 36, 158, 253, 3, 176, 61, 136, 147, 251, 43, 199, 27, 140, 42, 5, 199, 35, 150, 201, 212, 26, 155, 222, 158, 180, 80, 9, 40, 70, 125, 71, 214, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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