Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fce3b921d4d061680e4632e5c4e71e512170d7207f733c08acc29c38d74159e

Tx prefix hash: bec3276a256439be2fdc7fc344b702bef0b26ccf0e0aa8bfd32a022add927cae
Tx public key: 6ee3893a4a3d29f72fa434c96d68251a3b5038ede86fa3075663cf1ec3403e99
Timestamp: 1725128566 Timestamp [UCT]: 2024-08-31 18:22:46 Age [y:d:h:m:s]: 01:068:03:55:52
Block: 1100068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307164 RingCT/type: yes/0
Extra: 016ee3893a4a3d29f72fa434c96d68251a3b5038ede86fa3075663cf1ec3403e99021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb76a9b79747db56a0c163b2fc255a4828e0c348527a22e6b4d79b81d9f5c940 0.600000000000 1576041 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": 1100078, "vin": [ { "gen": { "height": 1100068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb76a9b79747db56a0c163b2fc255a4828e0c348527a22e6b4d79b81d9f5c940" } } ], "extra": [ 1, 110, 227, 137, 58, 74, 61, 41, 247, 47, 164, 52, 201, 109, 104, 37, 26, 59, 80, 56, 237, 232, 111, 163, 7, 86, 99, 207, 30, 195, 64, 62, 153, 2, 17, 0, 0, 0, 2, 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