Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2327df64aa7d8a58081ec8cfb95296df4cc017f189f60fa0bf50880e91f73742

Tx prefix hash: dcb7772f5ac9b8cf20d105ee357ccabce68392b702bc139a2f9bd6705583cb9a
Tx public key: 11a033d92d8502715a4b822a6db9a3d66caa8822747fc3ea177dab9408b86930
Timestamp: 1702106588 Timestamp [UCT]: 2023-12-09 07:23:08 Age [y:d:h:m:s]: 01:082:16:34:20
Block: 909200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320226 RingCT/type: yes/0
Extra: 0111a033d92d8502715a4b822a6db9a3d66caa8822747fc3ea177dab9408b8693002110000000a33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 653ec3242ae2ce1a73e923d4c98f7a0b5c3a0adb01c1b2917f55e7cdd9a7befa 0.600000000000 1366269 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": 909210, "vin": [ { "gen": { "height": 909200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "653ec3242ae2ce1a73e923d4c98f7a0b5c3a0adb01c1b2917f55e7cdd9a7befa" } } ], "extra": [ 1, 17, 160, 51, 217, 45, 133, 2, 113, 90, 75, 130, 42, 109, 185, 163, 214, 108, 170, 136, 34, 116, 127, 195, 234, 23, 125, 171, 148, 8, 184, 105, 48, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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