Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4af1d6672ef330ce129e77ed8f526b52a45e5749329de80229622a4039800a

Tx prefix hash: 5d7d50deb3b3ef33b5f7fee5ff67f4f7f1def3caac592a7320e6922b017590e1
Tx public key: 4f44511101c494b16665efb293a39bbf2f12608b31eaaf2f9cfe87338ea868d8
Timestamp: 1705329137 Timestamp [UCT]: 2024-01-15 14:32:17 Age [y:d:h:m:s]: 01:086:01:04:13
Block: 935911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322597 RingCT/type: yes/0
Extra: 014f44511101c494b16665efb293a39bbf2f12608b31eaaf2f9cfe87338ea868d80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03074b35ccdf96b504556e45ca762cc4b414e991f2ce8d45dd6e0e04807c2ccc 0.600000000000 1393929 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": 935921, "vin": [ { "gen": { "height": 935911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03074b35ccdf96b504556e45ca762cc4b414e991f2ce8d45dd6e0e04807c2ccc" } } ], "extra": [ 1, 79, 68, 81, 17, 1, 196, 148, 177, 102, 101, 239, 178, 147, 163, 155, 191, 47, 18, 96, 139, 49, 234, 175, 47, 156, 254, 135, 51, 142, 168, 104, 216, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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