Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7936f7988950c60c4eee2fef25555acad050e4f88de439a9f91afdcbdeb09fd

Tx prefix hash: 8a6f433faddaf7b0a0bc27c5a18c5b40e6feca333da887fdaa0c64929d0cff70
Tx public key: 28792741a6514ff8bd0fca1e058dad0b4dac78f5a237764a188b5569bb3cf62a
Timestamp: 1721711463 Timestamp [UCT]: 2024-07-23 05:11:03 Age [y:d:h:m:s]: 00:295:12:52:01
Block: 1071737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211180 RingCT/type: yes/0
Extra: 0128792741a6514ff8bd0fca1e058dad0b4dac78f5a237764a188b5569bb3cf62a02110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5df3f21538bc7f0ba929bfef09515e1e77e749c463bae85b583b25a9a5e7e731 0.600000000000 1544076 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": 1071747, "vin": [ { "gen": { "height": 1071737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5df3f21538bc7f0ba929bfef09515e1e77e749c463bae85b583b25a9a5e7e731" } } ], "extra": [ 1, 40, 121, 39, 65, 166, 81, 79, 248, 189, 15, 202, 30, 5, 141, 173, 11, 77, 172, 120, 245, 162, 55, 118, 74, 24, 139, 85, 105, 187, 60, 246, 42, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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