Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7a4c2f1d70784c9a57232c31a0cddf2cf09a821da2f25acdc392a8c8198a2f3

Tx prefix hash: b7a8cad1ce69b5a03df40be79f2d93e1551533bd33d60e5e596283451b8af60b
Tx public key: 9c7c04f81f1330b4392de9a26fa6a7dcb339c34eb6f2f839b76095b838e82617
Timestamp: 1717939507 Timestamp [UCT]: 2024-06-09 13:25:07 Age [y:d:h:m:s]: 01:158:03:43:36
Block: 1040471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371610 RingCT/type: yes/0
Extra: 019c7c04f81f1330b4392de9a26fa6a7dcb339c34eb6f2f839b76095b838e826170211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 338b50332e5f21c5fe0c1478c9dea7a2523c8f55c33d85357f7bba7108442ae8 0.600000000000 1509128 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": 1040481, "vin": [ { "gen": { "height": 1040471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338b50332e5f21c5fe0c1478c9dea7a2523c8f55c33d85357f7bba7108442ae8" } } ], "extra": [ 1, 156, 124, 4, 248, 31, 19, 48, 180, 57, 45, 233, 162, 111, 166, 167, 220, 179, 57, 195, 78, 182, 242, 248, 57, 183, 96, 149, 184, 56, 232, 38, 23, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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