Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 192b95ec2b479c0b2b422cc2f731ca9bc0ee4c45849e6d54faec9625b13765c3

Tx prefix hash: bffb3202ae5b358f0afac48cfb7affb9d78f5db5bf667a1f8a3294e9d0a4b8f9
Tx public key: f338ea4ffe3ce9439b0a691681ed55f155d27d661e3df676f07076579b7861af
Timestamp: 1728591560 Timestamp [UCT]: 2024-10-10 20:19:20 Age [y:d:h:m:s]: 00:175:15:00:32
Block: 1128790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125298 RingCT/type: yes/0
Extra: 01f338ea4ffe3ce9439b0a691681ed55f155d27d661e3df676f07076579b7861af02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 754ca363b7e5a87c9cc0b7cc219f2eb0fab4d51501adeea861d4eec2425b11f5 0.600000000000 1611613 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": 1128800, "vin": [ { "gen": { "height": 1128790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "754ca363b7e5a87c9cc0b7cc219f2eb0fab4d51501adeea861d4eec2425b11f5" } } ], "extra": [ 1, 243, 56, 234, 79, 254, 60, 233, 67, 155, 10, 105, 22, 129, 237, 85, 241, 85, 210, 125, 102, 30, 61, 246, 118, 240, 112, 118, 87, 155, 120, 97, 175, 2, 17, 0, 0, 0, 6, 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