Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0ba7eb3c8d66eacf01b2e9f63775612f1470035a85d5aa448884ac9dd1c5049

Tx prefix hash: 08dd3350afc3686825c5b3719ded6e7a30e3525cec1e5711d33ee5ff5181560a
Tx public key: 3df06e23a7086854da35d3f358f8e979701370e7eb2c2979ad7b258f7e0634cb
Timestamp: 1722409527 Timestamp [UCT]: 2024-07-31 07:05:27 Age [y:d:h:m:s]: 00:309:11:18:48
Block: 1077533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221123 RingCT/type: yes/0
Extra: 013df06e23a7086854da35d3f358f8e979701370e7eb2c2979ad7b258f7e0634cb021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e4a87d5599d94ca5e5e6fb93e5b8384ed6cf2110be03dba8f1e35dd146beb4b 0.600000000000 1550084 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": 1077543, "vin": [ { "gen": { "height": 1077533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e4a87d5599d94ca5e5e6fb93e5b8384ed6cf2110be03dba8f1e35dd146beb4b" } } ], "extra": [ 1, 61, 240, 110, 35, 167, 8, 104, 84, 218, 53, 211, 243, 88, 248, 233, 121, 112, 19, 112, 231, 235, 44, 41, 121, 173, 123, 37, 143, 126, 6, 52, 203, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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