Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8220790f6626d6b85e8512b366745dd33d4655d800dfad3d7f935914633a87f

Tx prefix hash: f00357e878aa594d74c5f068f5f8d04a27eaac2601067f123e6b5c646401b404
Tx public key: c9dfb16ddff24ed797bec35f4a7a2827a26f080a08664d4dbf7a22ea1ce1bec5
Timestamp: 1725150000 Timestamp [UCT]: 2024-09-01 00:20:00 Age [y:d:h:m:s]: 00:130:04:23:00
Block: 1100247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93110 RingCT/type: yes/0
Extra: 01c9dfb16ddff24ed797bec35f4a7a2827a26f080a08664d4dbf7a22ea1ce1bec502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d1f2d4b5cb708895bedd72edbfe2d34183f7207408731d00fdb71418eff872d 0.600000000000 1576222 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": 1100257, "vin": [ { "gen": { "height": 1100247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d1f2d4b5cb708895bedd72edbfe2d34183f7207408731d00fdb71418eff872d" } } ], "extra": [ 1, 201, 223, 177, 109, 223, 242, 78, 215, 151, 190, 195, 95, 74, 122, 40, 39, 162, 111, 8, 10, 8, 102, 77, 77, 191, 122, 34, 234, 28, 225, 190, 197, 2, 17, 0, 0, 0, 3, 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