Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 947fd732e3c7b95f9f9c66bc667be408abc8e3436654b2c405673433c1da9ce2

Tx prefix hash: f0e17b273451933b0e2b24b51dd707b07ba8378a1b6032ca572c758982b83f0d
Tx public key: 0cd21cc5891bc2b2060627c48c11f42ddb04f8ae919ed4650ea65ac230a26580
Timestamp: 1673663010 Timestamp [UCT]: 2023-01-14 02:23:30 Age [y:d:h:m:s]: 02:072:00:31:55
Block: 674253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 573137 RingCT/type: yes/0
Extra: 010cd21cc5891bc2b2060627c48c11f42ddb04f8ae919ed4650ea65ac230a265800211000000018b7b6602000000000000000000

1 output(s) for total of 3.580303691000 dcy

stealth address amount amount idx
00: 6fdd5b48475e5d4059c4b1d07d74efa30618da99dc217d29ef2bbd29ae2f208c 3.580303691000 1115898 of 0

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": 674263, "vin": [ { "gen": { "height": 674253 } } ], "vout": [ { "amount": 3580303691, "target": { "key": "6fdd5b48475e5d4059c4b1d07d74efa30618da99dc217d29ef2bbd29ae2f208c" } } ], "extra": [ 1, 12, 210, 28, 197, 137, 27, 194, 178, 6, 6, 39, 196, 140, 17, 244, 45, 219, 4, 248, 174, 145, 158, 212, 101, 14, 166, 90, 194, 48, 162, 101, 128, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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