Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37dea59b22e9f2c9c04c03eb5c750a834f2bff1d090787aaa2dd5dd9af6a9493

Tx prefix hash: 8b5d8d2d1d8b2dc9ca2c7a2c0ca60f88196c9632c065e15c23b2989af8d0f4c3
Tx public key: b872a11446feeb6a53ae67b16719e9da9d45caf8d4dd7a4d3a10a84a6fe0fde5
Timestamp: 1708738190 Timestamp [UCT]: 2024-02-24 01:29:50 Age [y:d:h:m:s]: 01:264:07:49:06
Block: 964191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447660 RingCT/type: yes/0
Extra: 01b872a11446feeb6a53ae67b16719e9da9d45caf8d4dd7a4d3a10a84a6fe0fde50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9071972b84b5e0cc6abafec28631fbb90d77ae329038ed27c0737c2e140507c2 0.600000000000 1423918 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": 964201, "vin": [ { "gen": { "height": 964191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9071972b84b5e0cc6abafec28631fbb90d77ae329038ed27c0737c2e140507c2" } } ], "extra": [ 1, 184, 114, 161, 20, 70, 254, 235, 106, 83, 174, 103, 177, 103, 25, 233, 218, 157, 69, 202, 248, 212, 221, 122, 77, 58, 16, 168, 74, 111, 224, 253, 229, 2, 17, 0, 0, 0, 1, 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