Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dacd40e945f13ae0589f20f2dc65e89c4407108f7391aedfb1eab09af2fb408e

Tx prefix hash: 6d98933f3791d7321b2cda91dee92f457420d6a0e7a76bc3790391db0e183c0e
Tx public key: f8b2490043bd768843d8a897c31becd36e235dbfd1379dc66db2f8ac0928c2cf
Timestamp: 1704122045 Timestamp [UCT]: 2024-01-01 15:14:05 Age [y:d:h:m:s]: 01:142:07:24:47
Block: 925910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362869 RingCT/type: yes/0
Extra: 01f8b2490043bd768843d8a897c31becd36e235dbfd1379dc66db2f8ac0928c2cf0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5863d5f07e1cde09f888fd6485ca19c57eef1a646c2d46d7f7b755a772ee6fa6 0.600000000000 1383680 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": 925920, "vin": [ { "gen": { "height": 925910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5863d5f07e1cde09f888fd6485ca19c57eef1a646c2d46d7f7b755a772ee6fa6" } } ], "extra": [ 1, 248, 178, 73, 0, 67, 189, 118, 136, 67, 216, 168, 151, 195, 27, 236, 211, 110, 35, 93, 191, 209, 55, 157, 198, 109, 178, 248, 172, 9, 40, 194, 207, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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