Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca4fc6aa827567b048a1448b210f7b47c6bf43b0a50b8cba61a90bd4a9c9578b

Tx prefix hash: fb020e0a3bb7bc088ad965f3cc209669bdbd0cd10412aae53272a777da77ab52
Tx public key: 8d9d5e07ccd3a176ba7da1b5417a02ebb6c72c5cd20765facba7b2340935f980
Timestamp: 1724512670 Timestamp [UCT]: 2024-08-24 15:17:50 Age [y:d:h:m:s]: 00:247:15:47:33
Block: 1094991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176861 RingCT/type: yes/0
Extra: 018d9d5e07ccd3a176ba7da1b5417a02ebb6c72c5cd20765facba7b2340935f980021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a579da643c1e3fb26da0015cde6d66d43a47d574bf599e64ae38d2c7cbb7884 0.600000000000 1570116 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": 1095001, "vin": [ { "gen": { "height": 1094991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a579da643c1e3fb26da0015cde6d66d43a47d574bf599e64ae38d2c7cbb7884" } } ], "extra": [ 1, 141, 157, 94, 7, 204, 211, 161, 118, 186, 125, 161, 181, 65, 122, 2, 235, 182, 199, 44, 92, 210, 7, 101, 250, 203, 167, 178, 52, 9, 53, 249, 128, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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