Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8f0245c3872964c30190ce28f719d5f8497fdaf131354286f2638897ea2f60f

Tx prefix hash: db2d6bd75f26632c3f5aa886f1ab757122ea30980f93ed7b8e0ea1cf05a748ea
Tx public key: 031cfc1c3e11df03d507a7b0c6d9a44b98cc8fe4ca4a692cefae00ca1667fafd
Timestamp: 1722177327 Timestamp [UCT]: 2024-07-28 14:35:27 Age [y:d:h:m:s]: 00:238:19:00:23
Block: 1075603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170561 RingCT/type: yes/0
Extra: 01031cfc1c3e11df03d507a7b0c6d9a44b98cc8fe4ca4a692cefae00ca1667fafd02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c90d813832a8020b507f6a8aa44c48c2c19f6006346671fea1d24231d8f0005 0.600000000000 1548132 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": 1075613, "vin": [ { "gen": { "height": 1075603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c90d813832a8020b507f6a8aa44c48c2c19f6006346671fea1d24231d8f0005" } } ], "extra": [ 1, 3, 28, 252, 28, 62, 17, 223, 3, 213, 7, 167, 176, 198, 217, 164, 75, 152, 204, 143, 228, 202, 74, 105, 44, 239, 174, 0, 202, 22, 103, 250, 253, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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