Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df2e6075bc3fd0a3ccc040be91046adf221b20ff0e04e57d101eafab7634d5c

Tx prefix hash: 94f5e6f44d5ed9698d959f116727c79cb0fa9e22801a551ed5038b8bb2e2f681
Tx public key: 046eed9f38f15443c2a67b2e888b21df7171fa6246d34378c241fdb710f8c809
Timestamp: 1731702954 Timestamp [UCT]: 2024-11-15 20:35:54 Age [y:d:h:m:s]: 00:140:05:05:20
Block: 1154483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100029 RingCT/type: yes/0
Extra: 01046eed9f38f15443c2a67b2e888b21df7171fa6246d34378c241fdb710f8c809021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5054abb36e51f1134735939f55fd4cc1226d31aef5fedfd7058885db185bacf 0.600000000000 1640096 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": 1154493, "vin": [ { "gen": { "height": 1154483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5054abb36e51f1134735939f55fd4cc1226d31aef5fedfd7058885db185bacf" } } ], "extra": [ 1, 4, 110, 237, 159, 56, 241, 84, 67, 194, 166, 123, 46, 136, 139, 33, 223, 113, 113, 250, 98, 70, 211, 67, 120, 194, 65, 253, 183, 16, 248, 200, 9, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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