Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973f4121a6b6557eef5d4bc9f51fbf55e6f2e474fe35a19b152193c8b3ac96ef

Tx prefix hash: 73ed6f718a702e65bf6c9c61336b273ef83ec34d246860e912f5c60c1c7016be
Tx public key: 8437b5a904a751e74292d2e99cf65161f0a34ef80b25226cb546ecfea8f3578f
Timestamp: 1721290043 Timestamp [UCT]: 2024-07-18 08:07:23 Age [y:d:h:m:s]: 01:108:16:01:16
Block: 1068265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336141 RingCT/type: yes/0
Extra: 018437b5a904a751e74292d2e99cf65161f0a34ef80b25226cb546ecfea8f3578f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1f64ff77958ff11889406374a5b37eabff10afa1b65feb50d049e4196ec22c4 0.600000000000 1539342 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": 1068275, "vin": [ { "gen": { "height": 1068265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1f64ff77958ff11889406374a5b37eabff10afa1b65feb50d049e4196ec22c4" } } ], "extra": [ 1, 132, 55, 181, 169, 4, 167, 81, 231, 66, 146, 210, 233, 156, 246, 81, 97, 240, 163, 78, 248, 11, 37, 34, 108, 181, 70, 236, 254, 168, 243, 87, 143, 2, 17, 0, 0, 0, 2, 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