Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a12c74b4766aad65c23b0977135d201e6387c64f5f16a3a6a4d7ef8965c429fa

Tx prefix hash: 84e0b4267e46808cc13caf4a4235562441a328f428bcac593516eab72abc1c3a
Tx public key: f0b8c5c76373b748ff8479805afc7a15b6756cf210015cd51b0e803d86a64e0b
Timestamp: 1731088926 Timestamp [UCT]: 2024-11-08 18:02:06 Age [y:d:h:m:s]: 00:131:03:52:06
Block: 1149405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93579 RingCT/type: yes/0
Extra: 01f0b8c5c76373b748ff8479805afc7a15b6756cf210015cd51b0e803d86a64e0b021100000012a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e66ca5a1f1e89c9036468fb3cae52861dd73bd284569efc99e49977b48b83d38 0.600000000000 1634476 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": 1149415, "vin": [ { "gen": { "height": 1149405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e66ca5a1f1e89c9036468fb3cae52861dd73bd284569efc99e49977b48b83d38" } } ], "extra": [ 1, 240, 184, 197, 199, 99, 115, 183, 72, 255, 132, 121, 128, 90, 252, 122, 21, 182, 117, 108, 242, 16, 1, 92, 213, 27, 14, 128, 61, 134, 166, 78, 11, 2, 17, 0, 0, 0, 18, 161, 29, 186, 152, 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